<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<HTML
><HEAD
><TITLE
>User Administration</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
REL="HOME"
TITLE="The Bugzilla Guide - 3.6.4 
    Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Bugzilla Configuration"
HREF="parameters.html"><LINK
REL="NEXT"
TITLE="Classifications"
HREF="classifications.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide - 3.6.4 
    Release</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="parameters.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 3. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="classifications.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="useradmin"
>3.2. User Administration</A
></H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="defaultuser"
>3.2.1. Creating the Default User</A
></H2
><P
>When you first run checksetup.pl after installing Bugzilla, it
      will prompt you for the administrative username (email address) and
      password for this "super user". If for some reason you delete
      the "super user" account, re-running checksetup.pl will again prompt
      you for this username and password.</P
><DIV
CLASS="tip"
><P
></P
><TABLE
CLASS="tip"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/tip.gif"
HSPACE="5"
ALT="Tip"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>If you wish to add more administrative users, add them to 
        the "admin" group and, optionally, edit the tweakparams, editusers,
        creategroups, editcomponents, and editkeywords groups to add the
        entire admin group to those groups (which is the case by default).
        </P
></TD
></TR
></TABLE
></DIV
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="manageusers"
>3.2.2. Managing Other Users</A
></H2
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="user-account-search"
>3.2.2.1. Searching for existing users</A
></H3
><P
>&#13;          If you have <SPAN
CLASS="QUOTE"
>"editusers"</SPAN
> privileges or if you are allowed
          to grant privileges for some groups, the <SPAN
CLASS="QUOTE"
>"Users"</SPAN
> link
          will appear in the Administration page.
        </P
><P
>&#13;          The first screen is a search form to search for existing user
          accounts. You can run searches based either on the user ID, real
          name or login name (i.e. the email address, or just the first part
          of the email address if the "emailsuffix" parameter is set).
          The search can be conducted
          in different ways using the listbox to the right of the text entry
          box. You can match by case-insensitive substring (the default),
          regular expression, a <EM
>reverse</EM
> regular expression
          match (which finds every user name which does NOT match the regular
          expression), or the exact string if you know exactly who you are
          looking for. The search can be restricted to users who are in a
          specific group. By default, the restriction is turned off.
        </P
><P
>&#13;          The search returns a list of
          users matching your criteria. User properties can be edited by clicking
          the login name. The Account History of a user can be viewed by clicking
          the "View" link in the Account History column. The Account History
          displays changes that have been made to the user account, the time of
          the change and the user who made the change. For example, the Account
          History page will display details of when a user was added or removed
          from a group.
        </P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="createnewusers"
>3.2.2.2. Creating new users</A
></H3
><DIV
CLASS="section"
><H4
CLASS="section"
><A
NAME="self-registration"
>3.2.2.2.1. Self-registration</A
></H4
><P
>&#13;            By default, users can create their own user accounts by clicking the
            <SPAN
CLASS="QUOTE"
>"New Account"</SPAN
> link at the bottom of each page (assuming
            they aren't logged in as someone else already). If you want to disable
            this self-registration, or if you want to restrict who can create his
            own user account, you have to edit the <SPAN
CLASS="QUOTE"
>"createemailregexp"</SPAN
>
            parameter in the <SPAN
CLASS="QUOTE"
>"Configuration"</SPAN
> page, see
            <A
HREF="parameters.html"
>Section 3.1</A
>.
          </P
></DIV
><DIV
CLASS="section"
><H4
CLASS="section"
><A
NAME="user-account-creation"
>3.2.2.2.2. Accounts created by an administrator</A
></H4
><P
>&#13;            Users with <SPAN
CLASS="QUOTE"
>"editusers"</SPAN
> privileges, such as administrators,
            can create user accounts for other users:
          </P
><P
></P
><OL
TYPE="1"
><LI
><P
>After logging in, click the "Users" link at the footer of
              the query page, and then click "Add a new user".</P
></LI
><LI
><P
>Fill out the form presented. This page is self-explanatory.
              When done, click "Submit".</P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>Adding a user this way will <EM
>not</EM
>
                send an email informing them of their username and password.
                While useful for creating dummy accounts (watchers which
                shuttle mail to another system, for instance, or email
                addresses which are a mailing list), in general it is
                preferable to log out and use the <SPAN
CLASS="QUOTE"
>"New Account"</SPAN
>
                button to create users, as it will pre-populate all the
                required fields and also notify the user of her account name
                and password.</P
></TD
></TR
></TABLE
></DIV
></LI
></OL
></DIV
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="modifyusers"
>3.2.2.3. Modifying Users</A
></H3
><P
>Once you have found your user, you can change the following
        fields:</P
><P
></P
><UL
><LI
><P
>&#13;            <EM
>Login Name</EM
>: 
            This is generally the user's full email address. However, if you
            have are using the <SPAN
CLASS="QUOTE"
>"emailsuffix"</SPAN
> parameter, this may
            just be the user's login name. Note that users can now change their
            login names themselves (to any valid email address).
            </P
></LI
><LI
><P
>&#13;            <EM
>Real Name</EM
>: The user's real name. Note that
            Bugzilla does not require this to create an account.</P
></LI
><LI
><P
>&#13;            <EM
>Password</EM
>: 
            You can change the user's password here. Users can automatically
            request a new password, so you shouldn't need to do this often.
            If you want to disable an account, see Disable Text below.
            </P
></LI
><LI
><P
>&#13;              <EM
>Bugmail Disabled</EM
>:
              Mark this checkbox to disable bugmail and whinemail completely
              for this account. This checkbox replaces the data/nomail file
              which existed in older versions of Bugzilla.
            </P
></LI
><LI
><P
>&#13;              <EM
>Disable Text</EM
>: 
              If you type anything in this box, including just a space, the
              user is prevented from logging in, or making any changes to 
              bugs via the web interface. 
              The HTML you type in this box is presented to the user when
              they attempt to perform these actions, and should explain
              why the account was disabled.
            </P
><P
>&#13;              Users with disabled accounts will continue to receive
              mail from Bugzilla; furthermore, they will not be able
              to log in themselves to change their own preferences and
              stop it. If you want an account (disabled or active) to
              stop receiving mail, simply check the
              <SPAN
CLASS="QUOTE"
>"Bugmail Disabled"</SPAN
> checkbox above.
            </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                Even users whose accounts have been disabled can still
                submit bugs via the e-mail gateway, if one exists.
                The e-mail gateway should <EM
>not</EM
> be
                enabled for secure installations of Bugzilla.
              </P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;                Don't disable all the administrator accounts!
              </P
></TD
></TR
></TABLE
></DIV
></LI
><LI
><P
>&#13;            <EM
>&#60;groupname&#62;</EM
>: 
            If you have created some groups, e.g. "securitysensitive", then
            checkboxes will appear here to allow you to add users to, or
            remove them from, these groups. The first checkbox gives the
            user the ability to add and remove other users as members of
            this group. The second checkbox adds the user himself as a member
            of the group.
            </P
></LI
><LI
><P
>&#13;            <EM
>canconfirm</EM
>: 
            This field is only used if you have enabled the "unconfirmed"
            status. If you enable this for a user,
            that user can then move bugs from "Unconfirmed" to a "Confirmed"
            status (e.g.: "New" status).</P
></LI
><LI
><P
>&#13;            <EM
>creategroups</EM
>: 
            This option will allow a user to create and destroy groups in
            Bugzilla.</P
></LI
><LI
><P
>&#13;            <EM
>editbugs</EM
>: 
            Unless a user has this bit set, they can only edit those bugs
            for which they are the assignee or the reporter. Even if this
            option is unchecked, users can still add comments to bugs.
            </P
></LI
><LI
><P
>&#13;            <EM
>editcomponents</EM
>: 
            This flag allows a user to create new products and components,
            as well as modify and destroy those that have no bugs associated
            with them. If a product or component has bugs associated with it,
            those bugs must be moved to a different product or component
            before Bugzilla will allow them to be destroyed.
            </P
></LI
><LI
><P
>&#13;            <EM
>editkeywords</EM
>: 
            If you use Bugzilla's keyword functionality, enabling this
            feature allows a user to create and destroy keywords. As always,
            the keywords for existing bugs containing the keyword the user
            wishes to destroy must be changed before Bugzilla will allow it
            to die.</P
></LI
><LI
><P
>&#13;            <EM
>editusers</EM
>: 
            This flag allows a user to do what you're doing right now: edit
            other users. This will allow those with the right to do so to
            remove administrator privileges from other users or grant them to
            themselves. Enable with care.</P
></LI
><LI
><P
>&#13;            <EM
>tweakparams</EM
>: 
            This flag allows a user to change Bugzilla's Params 
            (using <TT
CLASS="filename"
>editparams.cgi</TT
>.)</P
></LI
><LI
><P
> 
            <EM
>&#60;productname&#62;</EM
>:
            This allows an administrator to specify the products 
            in which a user can see bugs. If you turn on the 
            <SPAN
CLASS="QUOTE"
>"makeproductgroups"</SPAN
> parameter in
            the Group Security Panel in the Parameters page, 
            then Bugzilla creates one group per product (at the time you create 
            the product), and this group has exactly the same name as the 
            product itself. Note that for products that already exist when
            the parameter is turned on, the corresponding group will not be
            created. The user must still have the <SPAN
CLASS="QUOTE"
>"editbugs"</SPAN
> 
            privilege to edit bugs in these products.</P
></LI
></UL
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="user-account-deletion"
>3.2.2.4. Deleting Users</A
></H3
><P
>&#13;          If the <SPAN
CLASS="QUOTE"
>"allowuserdeletion"</SPAN
> parameter is turned on, see
          <A
HREF="parameters.html"
>Section 3.1</A
>, then you can also delete user accounts.
          Note that this is most of the time not the best thing to do. If only
          a warning in a yellow box is displayed, then the deletion is safe.
          If a warning is also displayed in a red box, then you should NOT try
          to delete the user account, else you will get referential integrity
          problems in your database, which can lead to unexpected behavior,
          such as bugs not appearing in bug lists anymore, or data displaying
          incorrectly. You have been warned!
        </P
></DIV
><DIV
CLASS="section"
><H3
CLASS="section"
><A
NAME="impersonatingusers"
>3.2.2.5. Impersonating Users</A
></H3
><P
>&#13;        There may be times when an administrator would like to do something as
        another user.  The <B
CLASS="command"
>sudo</B
> feature may be used to do 
        this.
        </P
><DIV
CLASS="note"
><P
></P
><TABLE
CLASS="note"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/note.gif"
HSPACE="5"
ALT="Note"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          To use the sudo feature, you must be in the
          <EM
>bz_sudoers</EM
> group.  By default, all
          administrators are in this group.</P
></TD
></TR
></TABLE
></DIV
><P
>&#13;        If you have access to this feature, you may start a session by
        going to the Edit Users page, Searching for a user and clicking on 
        their login.  You should see a link below their login name titled 
        "Impersonate this user".  Click on the link.  This will take you 
        to a page where you will see a description of the feature and 
        instructions for using it.  After reading the text, simply 
        enter the login of the user you would like to impersonate, provide 
        a short message explaining why you are doing this, and press the 
        button.</P
><P
>&#13;        As long as you are using this feature, everything you do will be done 
        as if you were logged in as the user you are impersonating.</P
><DIV
CLASS="warning"
><P
></P
><TABLE
CLASS="warning"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="../images/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>&#13;          The user you are impersonating will not be told about what you are 
          doing.  If you do anything that results in mail being sent, that 
          mail will appear to be from the user you are impersonating.  You 
          should be extremely careful while using this feature.</P
></TD
></TR
></TABLE
></DIV
></DIV
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="parameters.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="classifications.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Bugzilla Configuration</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Classifications</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>